I think that a standard is arising on the way a method is injected with a request bus. My naming was requestContext and I believe mach-ii and fusebox use both event. I think it would be benefitial for developers for me to change this to event. What are your thoughts on this? This would help if a developer wants to switch from one framework to another or doing a transition, if some of the similar elements shared in an MVC framework can remain the same. I am for changing it to event, but I would like to know you opinions?
Blog
Recent Entries
Your API Returns 200. Did the Business Transaction Actually Work?
The customer submits an order. The portal shows a confirmation. The API returns 200 OK, and the release checks pass.
The next morning, operations asks why the order never appeared in the approval queue. Support has a ticket. A developer has to trace the order through the database and figure out whether someone can safely submit it again.
For teams maintaining a ColdFusion or Lucee application, this is a frustrating kind of release failure: the team ...
Maria Jose Herrera
Maria Jose Herrera
November
11,
2026
BoxLang AI 3.7: Profiles, Embeddings Defaults and MCP Rate Limiting
Ortus Solutions announces the release of BoxLang AI 3.7. Name a provider, model, params and API key once, then pick it by name for a call, an agent, or a single agent run. Embeddings get their own defaults, MCP servers you build get rate limiting and trusted proxies, and a handful of important fixes land along the way.
Luis Majano
Luis Majano
November
05,
2026
BoxLang 1.19.0: See Everything Your Code Does
Ortus Solutions today announces the release of BoxLang 1.19.0, the software productivity platform for building, modernizing and running applications, with developers and AI agents working together. This release is about observability: built-in code coverage and execution profiling, the missing post-invocation events for BIFs, and new query and transaction events, and it pairs with the new BxLens beta, the debug bar and ops console that exposes hotspots and bytecode profilers. It also adds your own global settings in boxlang.json, static method interception, raw binary HTTP streaming and a lot of hardening across JDBC, Java interop and CFML compatibility.
Luis Majano
Luis Majano
November
05,
2026
Add Your Comment
(5)
Feb 27, 2007 14:48:06 UTC
by Sana
Hi Luis,
This makes perfect sense, should have some compatibility to other frameworks, at-least vocabulary should be same, so new developers adopt more easily.
Feb 27, 2007 16:20:13 UTC
by Sami Hoda
Can this be a customizable parameter instead?
Feb 27, 2007 18:07:03 UTC
by Luis Majano
I have been going over this and I think the best way is to just call the method and pass the argument. It would then be up to the developer to name the argument. However, the type of the argument will always be: coldbox.system.beans.requestContext
How does this sound?
Feb 27, 2007 19:09:58 UTC
by Sami Hoda
I suppose that works. Whenever there is a chance for flexibility, I'm for it.
Mar 05, 2007 19:19:15 UTC
by tony petruzzi
Actually most of the other frameworks let you change the name to whatever you want, they just use event as the default. But you are correct when saying that this would make it alot easier to transition from one framework to another.
BTW great work. ColdBox is getting more and more attention lately. I haven't heard anything coming out of the Model-Glue camp.